Managing contact status updates in a presence management system

ABSTRACT

A system configured to perform operations to receive, via a network communication interface, an indication of a power event occurring at a first device. The first device is for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The system is further configured to perform operations to hold, at a second device, at least one status update for an online contact of the online identity while the first device receives power from the internal battery. Furthermore, the system is configured to perform operations to release, for transmission to the first device, the at least one status update in response to determining that the first device switches back to the external power source.

TECHNICAL FIELD

Embodiments of the invention(s) generally relate to the field ofpresence management, and, more particularly, to contact status updatesin a presence management system.

BACKGROUND

Two typical concerns with users of mobile devices (e.g., cell phones,personal data assistants, etc.) are byte rate usage and power consumedby transmitting and receiving data while using an instant messaging typeapplication. Typically, mobile plans that offer data services overGeneral Packet Radio Service (GPRS) charge for the amount of bytes usedin a specific period of time. The bandwidth available to subscriberswith over the air network services, such as GPRS and Enhanced Data Ratesfor GSM Evolution (EDGE), is fairly limited. Using a number of deviceapplications, such as instant messenger (IM), a web browser, andsynchronization clients all at the same time consumes this limitedbandwidth and cause delays in data transmission.

SUMMARY

A system configured to perform operations to receive, via a networkcommunication interface, an indication of a power event occurring at afirst device. The first device is for an online identity. The powerevent causes the first device to switch from an external power source toan internal battery. The first device represents that the onlineidentity is online while the first device receives power from theinternal battery. The system is further configured to perform operationsto hold, at a second device, at least one status update for an onlinecontact of the online identity while the first device receives powerfrom the internal battery. Furthermore, the system is configured toperform operations to release, for transmission to the first device, theat least one status update in response to determining that the firstdevice switches back to the external power source.

BRIEF DESCRIPTION OF THE DRAWINGS

The present embodiments may be better understood, and numerous objects,features, and advantages made apparent to those skilled in the art byreferencing the accompanying drawings.

FIG. 1 depicts an example of a server holding a contact status updateafter a contact status update hold event occurs.

FIG. 2 depicts a flowchart of example operations for holding contactstatus updates.

FIG. 3 depicts an example presence management system that regulates flowof contact information based on priority values of contacts.

FIG. 4 depicts a flowchart of example operations for assigning priorityvalues to contacts.

FIG. 5 depicts a flowchart of example operations for dynamicallyupdating priority values of contacts.

FIG. 6 depicts an example presence management system communicatingcontact information with mapped values.

FIG. 7 depicts an example flowchart of example operations for writingcontact information using mapped values.

FIG. 8 depicts a flowchart of example operations for clearinginformation from a hierarchical extensible contact structure.

FIG. 9 depicts an example computer system.

DESCRIPTION OF EMBODIMENT(S)

The description that follows includes exemplary systems, methods,techniques, instruction sequences and computer program products thatembody techniques of the presently described embodiments of theinvention(s). However, it is understood that the described embodimentsmay be practiced without these specific details. For instance, althoughexamples refer to a contact list, contacts may be encoded in any of avariety of structures and embodiments should not be limited to list typestructures, such as a linked list or array. Example implementations of acontact list include hash tables, search trees, hybrids of trees andtables, etc. In other instances, well-known instruction instances,protocols, structures and techniques have not been shown in detail inorder not to obfuscate the description.

The following description uses the terms “identity,” “contact,”“presence management,” “presence management system.” The terms“identity” and “contact” are used to refer to a representation of auser, but from different perspectives. For example, a first user has anidentity “user1.” A contact list for “user1” includes a contact “user2.”A second user has the identity “user2,” and maintains a contact listthat includes contact “user1.” With respect to the first user, “user1”is an identity and “user2” is a contact. With respect to the seconduser, “user2” is an identity and “user1” is a contact. These two terms“identity” and “contact” are typically preceded in this description by“online” since these represent an online presence. The term “presencemanagement” is used to refer to functionality for managing of onlinepresence information for contacts. The term “presence management system”is used to refer to the devices (e.g., client, server, mobile phone,etc.) that read, write, communicate, process, and/or display presencemanagement information (e.g., status of contacts, contact information,etc.).

Managing online presence information for contacts involves propagatingcontact status updates from a contact to an interested identity. Acontact list may include hundreds to thousands of contacts for anidentity. When one of those contacts changes presence status (e.g., fromavailable to do-not-disturb), the change is propagated from a device ofthe contact, to a server, to one or more devices of the identitymaintaining the contact list. Although that single change or statusupdate consumes a small amount of resources, status updates for a largernumber of contacts occurring at various times consumes a moresubstantial amount of resources, including bandwidth and power. Althoughpower consumption may not be a factor for a desktop computer, powerconsumption for large scale and/or frequent status updates on deviceswith a more limited power source (e.g., mobile phones, personal dataassistants, etc.) may be a significant factor.

FIG. 1 depicts an example of a server holding a contact status updateafter a contact status update hold event occurs. A device 101 includes aclient contact list manager 102 and a contact list 103 for an identity“Mag.” The contact list 103 is depicted with contacts “Dad,” “Dan,”“Jus,” “Kim,” “CT2” with respective presence statuses of “MOBILE-DND”,“DND” (do-not-disturb), “ONLINE,” “ON PHONE,” “MOBILE.’ A presencestatus for Mag indicates “AVAILABLE.” A low power event occurs at thedevice 101 (e.g., the device goes into sleep mode due to lack of use,the device 101 switches from an external power source to an internalbattery, etc.). When the low power event is detected, the client contactlist manager 102 changes presence status for Mag from “AVAILABLE” to“INACTIVE.” A low power event is only one example of a contact statusupdate hold event. Other examples of a contact status update hold eventinclude a manual presence status change, an automatic presence statuschange, a manual low power event, an automatic low power event, a lowuse event, etc.

After the contact status update hold event, the client contact listmanager unit 102 causes a notification to be sent from the device 101 toa server 115 via a network 109. The notification notifies the server 115that the presence status of Mag has changed to “INACTIVE.” The server115 includes a server contact list manager 111, a contact list 105 forMag, and a master online contact list 107. The contact list 105 isdepicted with the same contacts as those in the contact list 103 at thedevice 101. The server 115 maintains a contact list for multipleidentities, including Mag. The contact list 105 for Mag is only depictedto avoid unnecessarily complicating the example illustration. The server115 also maintains the master online contact list 107. The master onlinecontact list 107 tracks presence status of all online contacts (i.e.,contacts that are “connected”). The active contact list 107 is depictedwith contacts “Mag,” “Dad,” “Dan,” “Jus,” “Kim,” “CT2,” and “UT7” withrespective presence statuses of “INACTIVE,” “MOBILE-DND,” “DND,”“ONLINE,” “ON PHONE,” “MOBILE,” and “IN OFFICE.” The server contact listmanager 111 propagates status updates for contacts in the active contactlist 107 to contact lists of interested identities.

In response to the notification from the device 101, the server contactlist manager 111 performs multiple updates. The server contact listmanager 111 updates the contact list 105 and the master online contactlist 107 to reflect the change in presence status for Mag to “INACTIVE.”The server contact list manager 111 also records an indication thatcontact status updates are to be held at the server 115 and not furtherpropagated to the device 101 due to the occurrence of the contact statusupdate event at the device (i.e., the presence status update toINACTIVE). In the example illustration of FIG. 1, the server contactlist manager 111 is depicted as updating a value (e.g., a bit) in thecontact list 105 to indicate that contact status updates are to bestalled at the server.

At some point, presence status for contact Jus changes from ONLINE toLUNCH. The server contact list manager 111 updates presence status forJus in the active contact list 107 and in the contact list 105 for Mag.The contact status update for Jus, however, is not delivered to thedevice 101. The server contact list manager 111 refrains from deliveringcontact status updates for Mag to the device 101 while the value or bitassociated with the contact list 105 is set to indicate contact statusupdates are to be held. Presence status for several contacts may change,perhaps multiple times, while this holding value is set. Indeed,presence status for a contact may change several times and eventuallyreturn to the presence state prior to the holding event. When areleasing event occurs, status updates for the contacts in the contactlist 105 are communicated to the device 101. A releasing event may occurat the server 115 or may occur at the device 101. Examples of areleasing event include expiration of a time period, notification fromthe device 101 to the server 115 that power source has changed, a useevent that indicates high use or normal use is communicated, anautomatic or manual change in status of Mag from INACTIVE to a moreactive presence status, a directive at the server 115 to communicatechanges in presence status, etc.

After a releasing event occurs, the task of determining which statusupdates to communicate may be implemented differently. In a firstexample, the server contact list manager 111 may maintain a currentpresence state for all contacts in a contact list and an initialpresence status for the contacts. After the release event, the servercontact list manager 111 walks the list and compares the current and theinitial presence status to determine which contacts have a differentpresence status since the hold value was set. In another example, eachcontact in a contact list is associated with a “dirty bit.” If a changein presence status occurs for a contact during the hold, then the servercontact list manager 111 sets the dirty bit, which indicates a changehas occurred. The server contact list manager 111 determines whichcontacts have their dirty bit set, and communicates contact statusupdates for those contacts.

In addition to implementing tasks differently, different implementationsmay store and organize the data differently. For example, contact listsdepicted in FIG. 1 most likely do not maintain redundant indications ofcontacts and in a monolithic contact list, although such implementationsare also possible. An embodiment may maintain a structure that isassociated with an identity, and references to contacts and theirinformation. The “contact list” at the server would identify theidentity (e.g., Mag) and have references (e.g., pointers, hash values,indices, etc.) to the master online contact list. In addition, a mastercontact list may not be limited to online contacts, and may alsoindicate offline contacts. In another embodiment, a comprehensivecontact list at a server represents presence status for contacts, andincludes (or references) a structure that identifies (e.g., by hashvalue, pointers, indices, etc.) interested identities. In yet anotherembodiment, the server contact list manager 111 may maintain a structureof hold values for identities separately from contact lists, and notnecessarily integrated into a contact list.

FIG. 2 depicts a flowchart of example operations for holding contactstatus updates. At block 201, a notification is received that a contactstatus update holding event has occurred at a device for identity XYZ.At block 203, a value is set to indicate that status updates forcontacts of XYZ are to be held. A dashed line from block 203 to block205 indicates that the flow of control is not necessarily at distincttimes (e.g., time that passes between operations of blocks 203 and 205may vary).

At block 205, a presence status update is received for a contact ABC,which is in the contact list of XYZ. At block 207, the received presencestatus updates for ABC is applied in a contact list of XYZ in a server.At block 209, a value is set to indicate that presence status haschanged for identity ABC. A dashed line represents flow of control fromblock 209 to block 211.

At block 211, a release event is detected that affects the XYZ contactlist. At block 213, those contacts in the XYZ contact list that havechanged presence status since the holding event are determined. At block215, the presence status of those contacts in the XYZ contact listdetermined to have changed presence status since the holding event arecommunicated to a device of the identity XYZ.

Holding presence status updates for contacts across a presencemanagement system reduces bandwidth consumption and power consumption.Fewer status updates are being communicated, thus less data is beingtransmitted across a network. Devices with limited power supplies handlefewer presence status updates for contacts, thus less power and cyclesare spent processing messages communicating status updates andtransmitting acknowledgements to such messages.

Communicating information about a contact, such as presence status, mayalso be regulated in accordance with priority values associated withcontacts. Various parameters about contacts with respect to a particularenvironment may be collected and utilized to assign priority values tothe contacts. Flow of information about the contacts is regulated basedon the assigned priority values. Information about contacts with higherpriority values may be communicated more frequently to client devicesfrom one or more servers than those contacts with lower priority values.In addition, information about contacts associated with priority valuesthat satisfy one or more criteria (e.g., threshold priority value) maybe prefetched from a server to a client device.

FIG. 3 depicts an example presence management system that regulates flowof contact information based on priority values of contacts. A presencemanagement system includes a device 301 and a sever 313 that communicatevia a network 315. The device 301 includes a contact prioritization unit307, a contact list 303 for an instant messaging application, and acontact list 305 for an e-mail application. The contact list 303 isdepicted with contacts Dad, Dan, Jus, Kim, and CT2. The contact list 305is depicted with contacts Dad, Jus, and Mag.

The contact prioritization unit 307 associates priority values withcontacts in the contact lists 303 and 305 based on pervasiveness of thecontacts and evaluation of data of the instant messaging application andthe e-mail application. The contact prioritization unit 307 may use anyof a number of prioritization schemes. Examples of prioritizationschemes include prioritizing based only on pervasiveness of contacts onthe device 301, prioritizing based only on evaluation of data ofapplications that use the contacts, prioritizing based on one or moreheuristics, or any combination of prioritizing schemes.

In FIG. 3, the contacts Dad and Jus occur in both contact lists 303 and305. The contacts Dad and Jus are assigned with priority values (orpreliminary priority values) higher than those assigned to the othercontacts, because Dad and Jus occur in both contact lists 303 and 305.The repeated occurrence of contacts in multiple contact lists suggestsmore frequent contact and/or a greater likelihood that these contactswill be accessed. The assigned priority values may be preliminarybecause the contact prioritization unit 307 may adjust the assignedpriority values based on other parameters, such as access history by auser, annotation and/or tags associated with contacts, etc. The contactprioritization unit 307 may also dynamically adjust assigned priorityvalues based on observed events, such as time of day contacts areaccessed, data transmitted to contacts, type of communications andcontent of communications to contacts, etc. In addition, applicationsmay be weighed differently, thus giving more weight to the contacts usedby the application(s) with greater weight.

The contact prioritization unit 307 communicates the priority values tothe server 313. The contact prioritization unit 307 also prefetchesinformation about contacts with the highest priority values (e.g., thosewith priority values above a given threshold). The server 313 includes acontact list 309, which is depicted as having the same contacts as thecontact list 303. A server contact list manager 311 associates thecommunicated priority values with the contacts in the contact list 309.At some point, a presence status update for CT2 is received. The servercontact list manager 311 updates the presence status of CT2 in thecontact list 309. The server contact list manager 311 then determinesthe priority value associated with CT2, and communicates the presencestatus update accordingly. For instance, information for contactsassociated with priority values of ‘A’ may be communicated immediately,whereas information for contacts associated with priority values of ‘C’may be communicated at the earliest of expiration of a time period or bypiggybacking on another message to the instant messaging application.

FIG. 4 depicts a flowchart of example operations for assigning priorityvalues to contacts. At block 401, a loop of operations begins for eachapplication that utilizes contacts. At block 403, contacts utilized bythe application are determined. For example, a list is built or contactsin an already existing list are marked.

At block 407, another loop of operations begins for each contactdetermined at block 403. At block 409, data related to the contact isexamined. For example, category tags are examined to determine businesscontacts and personal contacts. At block 411, one or more heuristics areapplied in light of the examined data to obtain a priority value for thecontact. For instance, greater priority values may be assigned tocontacts tagged as business contacts. At block 413, the contact isindicated in a contact prioritization list, unless already in theprioritization list. Also at block 413, the obtained priority value isassociated therewith. In one embodiment, a contact prioritization listis built separately from the existing contact lists. In anotherembodiment, one of the existing contact lists is used as the contactprioritization list. In another embodiment, one of the existing contactlists was defined to accommodate priority values for prioritization ofcontacts. At block 415, an application counter for the contact isincremented. At block 417, control either returns to block 407 orproceeds to block 419 if all of the contacts for the application havebeen evaluated. At block 419, control either returns to block 401 orproceeds to block 421 if there are no other applications that utilizecontacts.

At block 421, the priority value of each of the contacts is updatedbased on the corresponding application counter. At block 423, thepriority values are communicated to a server.

FIG. 5 depicts a flowchart of example operations for dynamicallyupdating priority values of contacts. At block 501, applications thatutilize contacts are monitored. At block 503, an event is detected atone of the monitored applications. At block 505, it is determined if thedetected event affects priority of any one of the contacts. If thedetected event affects one of the contacts, then control flows to block507. If not, then control flows back to block 501 for continuedmonitoring.

At block 507, a loop of operations begins for each affected contact. Atblock 509, an adjustment to the priority value associated with theaffected contact is determined based on the detected event. At block511, the priority value is adjusted based on the determined adjustment.At block 513, the contact is marked to indicate a change in priorityvalue. At block 514, control either loops back to block 507 or proceedsto block 515 if there are no other affected contacts. At block 515, thechanged priority values are communicated to a server.

The operations depicted in FIGS. 4 and 5 are intended to aid inunderstanding embodiments and should not be used to limit embodiments.For instance, priority values may be recalculated instead of adjusted.Embodiments may calculate one or more additional values and select apriority value based on another parameter. For example, a new priorityvalue may be calculated and then the old or new priority value selectedbased on time of day. As another example, block 513 may not be preformedas depicted. Embodiments may build a list of affected contacts and theirpriority values.

Furthermore, the above operations assume a client perspective.Operations for obtaining priority value or adjusting priority values maybe performed at a server. For example, a server may adjust priorityvalues based on detecting particular behavior from a client device(e.g., behavior suggesting a threatening or compromised client device).As another example, a server may set default priority values based oncurrent load on the server and communicate those priority values to aclient device.

Although the above illustrations depict more efficient communication ofcontact information with manipulation of message transmission frequency,contact information may also be communicated more efficiently withmanipulation of content of the messages. A presence management systemmay communicate contact information with mapped values. Contactinformation may be stored in a hierarchical extensible structure(“hierarchical extensible contact structure”). Devices in a presencemanagement system utilize a mapping scheme to map contact values (e.g.,e-mail address, phone number, etc.) to the appropriate field of thehierarchical extensible contact structure. When devices in the presencemanagement system communicate information for thousands of contacts,employing mapped values to navigate the hierarchical extensible contactstructure reduces the size of the messages, thus reducing resourceconsumption (e.g., bandwidth), particularly on the scale of anenterprise.

FIG. 6 depicts an example presence management system communicatingcontact information with mapped values. A client 619 includes ahierarchical extensible contact structure 607, a contact management unit603, and a representation of a contact mapping scheme 601. The contactstructure 607 includes a contact identifier “xyz@emailaddy.com.” Ane-mail address is used as a contact identifier for illustrativepurposes. Another value (e.g., a nickname, full legal name, mobile phonenumber, combination of name and number, etc.) may be used as a contactidentifier. The contact xyz@emailaddy.com is depicted as having thefollowing contact information:

-   -   Primary E-mail: xyz@emailaddy.com    -   Phone        -   Office: (555) 555-1234        -   Home: (555) 555-4321    -   Address        -   Home            -   Street: 100 This Street            -   City: Nowhere            -   State: Texas    -   Nickname: Inventor

In FIG. 6, the entry is depicted as also encoding the entry index “23.”The entry for the contact xyz@emailaddy.com may or may not encode theentry index. The contact mapping scheme representation 601 is depictedas mapping contact field identifiers (e.g., Primary E-mail, phone, etc.)to more compact values as follows:

-   -   <ENTRY INDEX>    -   Primary E-mail□1    -   Phone□2    -   Phone, Office□2,1    -   Phone, Home□2,2    -   Address□3    -   Address, Home□3,1    -   Address, Home, Street□3,1,1    -   Address, Home, City□3,1,2    -   Address, Home, State□3,1,3    -   Nickname□4

In FIG. 6, the contact list manager 601 receives contact information 605for xyz@emailaddy.com (e.g., a user inputs the information). The contactinformation includes a home street address of “100D This Street;” anOffice Phone number of “(555) 555-0000;” and Nickname “Co-Inventor.” Theclient contact list manager 603 updates the corresponding entry in thecontact structure 607 with the contact information. The client contactlist manager 603 then determines mappings for the fields updated withthe contact information. With the mapping scheme representation 601, theclient contact list manager 603 determines the following mappings: HomeStreet Address maps to “3,1,1;” Office Phone maps to “2,2;” and Nicknamemaps to “4.” The client contact list manager 603 generates a compactupdate message 609 using the mapped values for contact fieldidentifiers, and communicates the new contact information with thecompact update message 609 to a server 617. The compact update message609 encodes the information as follows:

-   -   23, 2, 1, “(555) 555-0000”,    -   3, 1, 1, “100D This Street”,    -   4, “Co-Inventor”

The server 617 that receives the compact update message 609 includes aserver contact list manager 611, a contact mapping scheme 613, and ahierarchical extensible contact structure 615. The contact mappingscheme representation 613 represents the same mapping scheme as themapping scheme representation 601. Different techniques can be used toestablish the mapping scheme between the client 619 and the server 617.Examples include the client 619 and the server 617 negotiating toestablish the mapping scheme, the client 619 selecting a mapping schemeand communicating the selection to the server 617, the server 617selecting a mapping scheme and communicating the selected mapping schemeto the client 619, etc. The hierarchical extensible contact structure615 includes an entry for the contact xyz@emailaddy.com.

The server contact list manager 611 updates the contact structure 615with the contact information in the message 609 in accordance with themapping represented by the contact mapping scheme representation 613.The server contact list manager 611 determines that xyz@emailaddy.commaps to entry “23.” A number of techniques are available for mappingentries to mapping values and may vary with the type of structure(s)used to store contact information. Examples of mapping schemes forentries include numbering of entries, hashing identifying values (e.g.,the primary e-mail address), etc. Further, embodiments may use onemapping scheme for the values that identify entries and another mappingscheme for fields and subfields of an entry. After determining thatentry 23 maps to xyz@emailaddy.com, the server contact list manager 611maps “2,1” to the field “Phone” and subfield “Office.” The servercontact list manager 611 maps “3,1,1” to the field “Address” andsubfields “Home” then “Street.” The server contact list manager 611 alsomaps “4” to the field “Nickname.”

FIG. 7 depicts an example flowchart of example operations for writingcontact information using mapped values. At block 701, an update messagewith one or more values for a contact and mapped contact field values isreceived. At block 702, the first value of the received message is read.At block 703, it is determined if the hierarchical extensible contactlist structure includes an entry that corresponds to the first readvalue. If the first read value corresponds to an entry in the contactlist structure, then control flows to block 707. If not, then controlflows to block 705.

At block 705, an entry is added to the contact list structure for thefirst read value. Control flows from block 705 to block 707.

At block 707, the entry, either the newly added entry or the matchingentry, is selected in the contact list structure. At block 709, the nextvalue in the message is read. At block 711, the read value is mapped toa corresponding contact field of the entry. At block 713, the next valuein the message is read. At block 715, it is determined if the read valueis a mapped value or a contact field value. For example, a mapped valuemay be a first data type (e.g., integer), whereas a contact field valueis read as a second data type (e.g., string literal). In anotherexample, delimiters may be used to distinguish mapped values fromcontact field values. As another example, messages may be structured ina manner so that location of a read value can be used to ascertainwhether the read value is a mapped value or a contact field value. Ifthe read value is a mapped value, then control flows to block 717. Ifthe read value is a contact field value, then control flows to block719.

At block 717, the read mapped value is mapped to a correspondingsubfield. Control flows from block 717 back to block 713.

At block 719, the contact field value is written into the mapped fieldor subfield. At block 721, it is determined if the end of the messagehas been reached. If the end of the message has been reached, thencontrol flows to block 723. If the message still has more values to beread, then control flows back to block 709.

At block 723, successful update of the selected entry is confirmed.

It should be understood that the above operations are used as examplesto illustrate embodiments and should not be used to limit embodiments.For example, values may not be read from a message. When a message isreceived, the message may be parsed into components and stored intodifferent buffers read by different processes. As another example,mapping indices may not be read individually. For example, delimitersmay be used to identify the end of a string of mapped values. A contactlist manager or associated process or thread may continue reading allmapped values until reading a mapped value delimiter. The aggregate ofread values are then used to map directly to a subfield instead ofwalking from a parent field down each level of subfield.

FIG. 8 depicts a flowchart of example operations for clearinginformation from a hierarchical extensible contact structure. At block801, a remove message is received for a contact. At block 802, the firstvalue of the remove message is read. At block 803, it is determined ifthe contact list structure includes an entry that corresponds to thefirst read value. If the first read value does not correspond to a firstread value, then control flows to block 805. If the first read valuecorresponds to an entry, then control flows to block 807.

At block 805, a notification is generated to indicate that the contactis not in the list.

At block 807, the entry that corresponds to the first read entry isselected. At block 809, a value(s) is read up to a mapped valuedelimiter. At block 811, the read value(s) is mapped to a correspondingfield or subfield of the selected entry. At block 813, it is determinedif the mapped field or subfield hosts a contact field value or is ahierarchy label (e.g., Phone may be a label for Office and Home phonenumbers). If the mapped field or subfield hosts a value, then controlflows to block 815. If the mapped field or subfield operates as ahierarchy label, then control flows to block 821.

At block 815, the contact field value is cleared. At block 817, it isdetermined if the end of the remove message has been reached. If the endof message has been reached, then control flows to block 819. If the endof message has not been reached, then control flows to block 809.

At block 819, processing of the remove message is confirmed.

At block 821, a prompt is made for confirmation that all subfields areto be cleared. If it is confirmed that all subfields of the hierarchylabel are to be cleared, then control flows to block 823. If it is notconfirmed, then control flows to block 825.

At block 823, the values of the subfields are cleared. Control flowsfrom block 823 to block 817.

At block 825, subfields under the hierarchy label are presented and aprompt is made for selection of particular ones of the presentedsubfields for clearing of values. At block 827, values of any selectedsubfields are cleared. Control flows from block 827 to block 817.

The example operations depicted in the flowcharts of FIGS. 7 and 8assume a message has information for one contact. A message may haveinformation for multiple contacts. Each contact in a message may beidentified by data type, value size, contact delimiters, etc. Inaddition, the operations in FIG. 8 may be different to accommodatemessage that include commands that designate remove operations. Insteadof determining whether to clear a particular field value or values ofall subfields, a user may designate and the message encode a commandthat represents the designation. Further, additional operations may beperformed. For instance, addition of an entry or reassigning an entryfor a different field or subfield may incur operations to update themapping scheme representation.

Using direct mapping allows efficient communication of contactinformation for a contact represented with one or more hierarchicalextensible contact structures. When communications for contacts are madeon the scale of thousands, the resources conserved with this efficientcommunication is substantial. In addition, this direct mapping allowsfor flexibility with the contact structure without disrupting themapping. Every entry can be re-indexed as needed and the updated datastructure kept in synchronization between devices (e.g., a server deviceand client devices). For instance, as multiple phone number entries aredeleted and new ones are added, the new ones can take the place of theold ones. Referring to FIG. 6 as an illustration, the contact structuremay be modified to list a business address instead of a home address.Although the home field would be removed, the mapping for home addresselements can be reused for business address elements. This flexibilityand recycling keeps the mapping compact.

The described embodiments may be provided as a computer program product,or software, that may include a machine-readable medium having storedthereon instructions, which may be used to program a computer system (orother electronic device(s)) to perform a process according toembodiments of the invention(s), whether presently described or not,since every conceivable variation is not enumerated herein. A machinereadable medium includes any mechanism for storing (“machine readablestorage medium”) or transmitting (“machine readable signal medium”)information in a form (e.g., software, processing application) readableby a machine (e.g., a computer). The machine-readable storage medium mayinclude, but is not limited to, magnetic storage medium (e.g., floppydiskette); optical storage medium (e.g., CD-ROM); magneto-opticalstorage medium; read only memory (ROM); random access memory (RAM);erasable programmable memory (e.g., EPROM and EEPROM); flash memory; orother types of medium suitable for storing electronic instructions. Inaddition, embodiments may be embodied in a machine readable signalmedium that may include an electrical, optical, acoustical or other formof propagated signal (e.g., carrier waves, infrared signals, digitalsignals, etc.), or wireline, wireless, or other communications medium.

FIG. 9 depicts an example computer system. A computer system includes aprocessor unit 901 (possibly including multiple processors, multiplecores, multiple nodes, and/or implementing multi-threading, etc.). Thecomputer system includes memory 907. The memory 907 may be system memory(e.g., one or more of cache, SRAM, DRAM, zero capacitor RAM, TwinTransistor RAM, eDRAM, EDO RAM, DDR RAM, EEPROM, NRAM, RRAM, SONOS,PRAM, etc.) or any one or more of the above already described possiblerealizations of machine-readable media. The computer system alsoincludes a bus 903 (e.g., PCI, ISA, PCI-Express, HyperTransport®,InfiniBand®, NuBus, etc.), a network interface 909 (e.g., an ATMinterface, an Ethernet interface, a Frame Relay interface, SONETinterface, wireless interface, etc.), and a storage device(s) 911 (e.g.,optical storage, magnetic storage, etc.). The system also includes acontact list manager 921. The contact list manager 921 is configured toperform any one or more of the functionalities above for holding and/orreleasing contact status updates, prioritizing contacts, regulating flowof contact information based on priority values of contacts, and mappingfields and subfields of a hierarchical extensible contact structure.Although depicted as a separate unit, the contact list manager 921 maybe implemented as software encoded in the memory 907, logic in theprocessing unit 901, as both software and hardware, etc. Further,realizations may include fewer or additional components not illustratedin FIG. 9 (e.g., video cards, audio cards, additional networkinterfaces, peripheral devices, etc.). The processor unit 901, thestorage device(s) 911, the contact list manager 921, and the networkinterface 909 are coupled to the bus 903. Although illustrated as beingcoupled to the bus 903, the memory 907 may be coupled to the processorunit 901.

While the embodiments are described with reference to variousimplementations and exploitations, it will be understood that theseembodiments are illustrative and that the scope of the invention(s) isnot limited to them. In general, techniques for holding and/or releasingcontact status updates, prioritizing contacts, regulating flow ofcontact information based on priority values of contacts, and mappingfields and subfields of a hierarchical extensible contact structure asdescribed herein may be implemented with facilities consistent with anyhardware system or hardware systems. Many variations, modifications,additions, and improvements are possible.

Further, presence status update for an online contact does not require auser to change presence status on a presence management application at acomputer. As stated earlier, presence status can be maintained on avariety of devices including mobile phones, smart phones, laptops,personal data assistants, game consoles, etc. In addition, a change inpresence status does not require interaction (or lack of interaction,e.g., a change to idle status) by a user. For example, missing a call toa mobile phone can trigger a change in presence status for the contactassociated with the mobile phone. As another example, a server cantrigger a change in presence status for contacts maintained by theserver (e.g., a server forces all presence status to “temporarilyunavailable” when network traffic reaches a given threshold).

Plural instances may be provided for components, operations orstructures described herein as a single instance. Finally, boundariesbetween various components, operations and data stores are somewhatarbitrary, and particular operations are illustrated in the context ofspecific illustrative configurations. Other allocations of functionalityare envisioned and may fall within the scope of the invention(s). Ingeneral, structures and functionality presented as separate componentsin the exemplary configurations may be implemented as a combinedstructure or component. Similarly, structures and functionalitypresented as a single component may be implemented as separatecomponents. These and other variations, modifications, additions, andimprovements may fall within the scope of the invention(s).

What is claimed is:
 1. A method for managing online status according toa power event comprising: receiving, via a network communicationinterface, an indication of the power event occurring at a first devicefor an online identity, wherein the power event causes the first deviceto switch from an external power source to an internal battery, andwherein the first device represents that the online identity is onlinewhile the first device receives power from the internal battery;holding, at a second device, at least one status update for an onlinecontact of the online identity while the first device receives powerfrom the internal battery; and releasing, for transmission to the firstdevice, the at least one status update in response to determining thatthe first device switches back to the external power source.
 2. Themethod of claim 1, wherein the power event comprises one of a manualevent and an automatic event.
 3. The method of claim 1, wherein the atleast one status update represents a net change to a status of theonline contact.
 4. The method of claim 1 further comprising piggybackingthe at least one status update on other data transmitted to the firstdevice.
 5. The method of claim 1, wherein the first device transmitsstatus messages less frequently than before the power event.
 6. Themethod of claim 1 further comprising resetting status of the onlineidentity if a keep alive message is not received within a given timeperiod.
 7. The method of claim 1 further comprising holding, at thesecond device, the at least one status update in response to determininga specific level of interest by the online identity.
 8. A non-transitorymachine-readable storage medium having stored therein a program product,which when executed by a set of one or more processor units cause theset of one or more processors units to perform operations comprising:receiving, via a network communication interface, an indication of apower event occurring at a first device for an online identity, whereinthe power event causes the first device to switch from an external powersource to an internal battery, and wherein the first device representsthat the online identity is online while the first device receives powerfrom the internal battery; holding, at a second device, at least onestatus update for an online contact of the online identity while thefirst device receives power from the internal battery; and releasing,for transmission to the first device, the at least one status update inresponse to determining that the first device switches back to theexternal power source.
 9. The non-transitory machine-readable storagemedium of claim 8, wherein the power event comprises one of a manualevent and an automatic event.
 10. The non-transitory machine-readablestorage medium of claim 8, wherein the at least one status updaterepresents a net change to a status of the online contact.
 11. Thenon-transitory machine-readable storage medium of claim 8, saidoperations further comprising piggybacking the at least one statusupdate on other data transmitted to the first device.
 12. Thenon-transitory machine-readable storage medium of claim 8, wherein thefirst device transmits status messages less frequently than before thepower event.
 13. The non-transitory machine-readable storage medium ofclaim 8, said operations further comprising resetting status of theonline identity if a keep alive message is not received within a giventime period.
 14. The non-transitory machine-readable storage medium ofclaim 8, said operations further comprising holding, at the seconddevice, the at least one status update in response to determining aspecific level of interest by the online identity.
 15. An apparatuscomprising: a processor; a network interface coupled with the processorand configured to transmit and receive data; and a memory storage deviceconfigured to store instructions, which when executed by the processorcause the apparatus to perform operations to receive, via the networkinterface, an indication of a power event occurring at a first devicefor an online identity, wherein the power event causes the first deviceto switch from an external power source to an internal battery, andwherein the first device represents that the online identity is onlinewhile the first device receives power from the internal battery, hold,at a second device, at least one status update for an online contact ofthe online identity while the first device receives power from theinternal battery, and release, for transmission to the first device, theat least one status update in response to determination that the firstdevice switches back to the external power source.
 16. The apparatus ofclaim 15, wherein the power event comprises one of a manual event and anautomatic event.
 17. The apparatus of claim 15, wherein the at least onestatus update represents a net change to a status of the online contact.18. The apparatus of claim 15, wherein the memory storage device isconfigured to store instructions, which, when executed by the processor,cause the apparatus to perform operations to piggyback the at least onestatus update on other data transmitted to the first device.
 19. Theapparatus of claim 15, wherein the memory storage device is configuredto store instructions, which, when executed by the processor, cause theapparatus to perform operations to reset status of the online identityif a keep alive message is not received within a given time period. 20.The apparatus of claim 15, wherein the memory storage device isconfigured to store instructions, which, when executed by the processor,cause the apparatus to perform operations to hold, at the second device,the at least one status update in response to determination of aspecific level of interest by the online identity.